The EDB Postgres Advanced Server must generate audit records when unsuccessful attempts to access security objects occur.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-69029	PPS9-00-010100	SV-83633r1_rule		Medium

Description
Changes to the security configuration must be tracked. This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Description

Changes to the security configuration must be tracked. This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

STIG	Date
EDB Postgres Advanced Server Security Technical Implementation Guide	2016-08-19

Details

Check Text ( C-69503r1_chk )
Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all", this is a finding.

Fix Text (F-75215r1_fix)
Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf();